The driver will pick a car to view. Each car will have a screen that will include:
Current status and needs (mileage, needs transmission fluid flushed)
History of inspections by user (tutorials), for example, tire tread, oil, belts, etc.
History of what service was done, for example tires are new, oil was changed 1000 miles and 1 month ago, etc.
History of maintenance providers and locations. Includes history of the ratings the driver provided.
It should be possible to search the vehicle-history and to limit the view of the vehicle history. For example, a driver might only want to see history of oil changes.
A driver should be able to view a history of all of their prompts. They should also be able to view quiz history, inspection/tutorial history, and maintenance-action history.
Aside from the Queue prompts, these entries should be in 'story form.' For example:
"On [date], Bekkah took a quiz asking [question1] & [question2]. She answered [answer] and got the answer correct. She gained [##] points, and became a [next level]."
If points are assessed, this should be noted in the story, and if the points result in a 'level up,' this should also be noted.
Queue
The prompt queue, "Queue" window should have a list of all of the prompts that have been put on hold by the user. This view should have the prompt title, and each prompt should be expandable to show details. There should also be a way to re-order the queues and a path to complete the queued prompt from there (exception being the quiz).
Quizzes
The "Quizzes" tab will be a history of all of the quiz prompts the User has completed. There should be an area for data visualizations on top (think Google Analytics), and for each entry, there should be:
Date
Quiz question(s)
User's Answer
Correct Answer (if different)
The amount of points the user gained towards their next level
Each entry should be color coded by the "user's correctness"
Status/Maintenance Stories
This tab will house the results of prompts sent to the User merely for collecting information on the status of the car. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:
Date
Information requested
User's answer
Points gained towards next level (if relevant)
Service Stories
This tab will house stories related to users taking action to service their vehicle at a service station, by themselves or by someone else. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:
Date
Person who performed service if not Service Station (link to profile if possible)
Service Station (link to profile if possible)
Technician (if relevant)
Location
Services performed
Car involved (if relevant)
Experience rating (review) if relevant
If no review was posted, there should be a path for the user to do so from that view.
Research and Results
This will viewable via the AutoMindr application or on the web with and without notification. It is simply a view of the cars current status and any previous history on it, as far as services. This depending on the setting options can be viewed by others who are not the primary driver, and may include buddies, mentors or mechanics.
When conducting research and doing testing, we will want 9 out of 10 users to be able to retrieve this information quickly and easily.
Metrics for success
If users want to view the current status and the history of their car without being prompted, we will know that AutoMindr is working, making the user more aware of their car and having them think about it more often.
Future Steps
AutoMindr will allow users to print off this documentation, to have and take with them to scheduling appointments if they would like.
Screen
The driver will pick a car to view. Each car will have a screen that will include:
- Current status and needs (mileage, needs transmission fluid flushed)
- History of inspections by user (tutorials), for example, tire tread, oil, belts, etc.
- History of what service was done, for example tires are new, oil was changed 1000 miles and 1 month ago, etc.
- History of maintenance providers and locations. Includes history of the ratings the driver provided.
It should be possible to search the vehicle-history and to limit the view of the vehicle history. For example, a driver might only want to see history of oil changes.A driver should be able to view a history of all of their prompts. They should also be able to view quiz history, inspection/tutorial history, and maintenance-action history.
Aside from the Queue prompts, these entries should be in 'story form.' For example:
"On [date], Bekkah took a quiz asking [question1] & [question2]. She answered [answer] and got the answer correct. She gained [##] points, and became a [next level]."
If points are assessed, this should be noted in the story, and if the points result in a 'level up,' this should also be noted.
Queue
The prompt queue, "Queue" window should have a list of all of the prompts that have been put on hold by the user. This view should have the prompt title, and each prompt should be expandable to show details. There should also be a way to re-order the queues and a path to complete the queued prompt from there (exception being the quiz).Quizzes
The "Quizzes" tab will be a history of all of the quiz prompts the User has completed. There should be an area for data visualizations on top (think Google Analytics), and for each entry, there should be:Status/Maintenance Stories
This tab will house the results of prompts sent to the User merely for collecting information on the status of the car. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:Service Stories
This tab will house stories related to users taking action to service their vehicle at a service station, by themselves or by someone else. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:Research and Results
This will viewable via the AutoMindr application or on the web with and without notification. It is simply a view of the cars current status and any previous history on it, as far as services. This depending on the setting options can be viewed by others who are not the primary driver, and may include buddies, mentors or mechanics.When conducting research and doing testing, we will want 9 out of 10 users to be able to retrieve this information quickly and easily.
Metrics for success
If users want to view the current status and the history of their car without being prompted, we will know that AutoMindr is working, making the user more aware of their car and having them think about it more often.Future Steps
AutoMindr will allow users to print off this documentation, to have and take with them to scheduling appointments if they would like.